Skip to content

[Do not merge] - Dataview perf improvements poc#4

Closed
michaelolo24 wants to merge 1 commit intolgestc:default_data_view_initfrom
michaelolo24:dv-perf-improvements-poc
Closed

[Do not merge] - Dataview perf improvements poc#4
michaelolo24 wants to merge 1 commit intolgestc:default_data_view_initfrom
michaelolo24:dv-perf-improvements-poc

Conversation

@michaelolo24
Copy link

Summary

Test with minimum 300k+ fields in the index mapping and documents containing fields populated to that extent

Summarize your PR. If it involves visual changes include a screenshot or gif.

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

  • Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
  • Documentation was added for features that require explanation or tutorials
  • Unit or functional tests were updated or added to match the most common scenarios
  • If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
  • This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
  • Flaky Test Runner was used on any tests changed
  • The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

@michaelolo24 michaelolo24 changed the base branch from main to default_data_view_init June 10, 2025 02:39
</DiscoverInTimelineContextProvider>
</UpsellingProvider>
</CellActionsProvider>
<ReactQueryDevtools initialIsOpen={false} />
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs to be here to account for providers above the cases context

<Route path="/">
<CasesContext owner={[APP_ID]} permissions={userCasesPermissions}>
<HomePage>{children}</HomePage>
<ReactQueryClientProvider>
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cases context has it's own queryClient which we need to re-override, but need to test this behavior. This is primarily useful just for our testing purposes

@michaelolo24 michaelolo24 force-pushed the dv-perf-improvements-poc branch from 9ae1546 to 95f4cd5 Compare June 11, 2025 03:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant